Copper Work Order API

To get support from our team and view the status of the APIs, view our Support page.

Question

Why do the GET events only apply to orders transitioned into the “dispatch” OR “In progress” stage?

Answer

GET Events is limited to dispatch OR in progress, as this reflects a core limitation from ICMS. ICMS can only generate events when orders are transitioned to certain stages and dispatch is the earliest stage available in the Service order Lifecycle. We also allow In progress where a Service Partner wishes to validate manually before taking the order from ICMS into their system using the API.

Question

Is the Address the same as the ICMS SAM ID?

Answer

The address provided through the Work Order API is the same address captured for a Fibre order. The address at capture is driven from the address API, which in turn uses a common address dataset for Fibre services for all Chorus applications.

Question

Why do the work instructions appear incorrectly formatted at times?

Answer

When the customer ordering capabilities for fibre were established, Chorus recognised that the only way to convey the structured work instructions was to use the text based memo field. While this is templated, there are rare occasions where the content will not be parsed correctly thereby producing incorrectly formatted instructions.